Add RABBITMQ_MAX_OPEN_FILES variable to the startup script (backport #14410) #14411
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In some environments it may be tricky to run a command before RabbitMQ is started. Kubernetes For example, upgrading to Containerd 2.0 accidentally lowered the value of available descriptors in GKE (https://cloud.google.com/kubernetes-engine/docs/troubleshooting/known-issues#containerd-ulimit-reduced). While this particular issue is resolved in newer GKE versions, it was a good example of why a variable like this would be helpful. Kubernetes-level solutions (on the node or with a daemonset) would require a different level of access for users. (cherry picked from commit ad3fccf)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: this does not override the existing recommendations for overriding the kernel file handle limit.
In some environments it may be tricky to run a command before RabbitMQ is started. Kubernetes For example, upgrading to Containerd 2.0 accidentally lowered the value of available descriptors in GKE
(https://cloud.google.com/kubernetes-engine/docs/troubleshooting/known-issues#containerd-ulimit-reduced). While this particular issue is resolved in newer GKE versions, it was a good example of why a variable like this would be helpful. Kubernetes-level solutions (on the node or with a daemonset) would require a different level of access for users.
This is an automatic backport of pull request #14410 done by Mergify.